<html>
<head><meta charset="utf-8"><title>Promoting packed_simd to std::simd · t-lang/meta · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/index.html">t-lang/meta</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html">Promoting packed_simd to std::simd</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="201596344"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201596344" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Henri Sivonen <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201596344">(Jun 22 2020 at 11:56)</a>:</h4>
<p>It appears that work on <a href="https://github.com/rust-lang/rfcs/pull/2366">https://github.com/rust-lang/rfcs/pull/2366</a> and <code>packed_simd</code> has stalled due to lack of roadmap commitment: <a href="https://github.com/rust-lang/packed_simd/issues/213#issuecomment-549282056">https://github.com/rust-lang/packed_simd/issues/213#issuecomment-549282056</a> .</p>
<p>How could we get consensus at least on the 128-bit part of <code>packed_simd</code> to become <code>std::simd</code>? The formulation of the types was waiting for const generics, but: 1) the user will use <code>u8x16</code>, <code>u16x8</code>, etc., anyway without caring about the lower-level formulation and 2) the types need to be zero-cost transmutable to <code>core::arch</code> types anyway, so low-level representation issues are already constrained by whatever has been shipped to stable under <code>core::arch</code>.</p>



<a name="201776949"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201776949" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201776949">(Jun 23 2020 at 20:18)</a>:</h4>
<p>As mentioned by email, I think the next step would be to file an MCP for a portable SIMD project group, to consider what the shape of portable SIMD in std should look like.</p>



<a name="201777007"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201777007" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201777007">(Jun 23 2020 at 20:19)</a>:</h4>
<p>This is likely something that crosses over between libs and lang, which should be doable given appropriate liaisons from both teams.</p>



<a name="201777295"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201777295" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201777295">(Jun 23 2020 at 20:21)</a>:</h4>
<p>I would also not take it as a given that the correct outcome will be to merge an unmodified version of any particular crate from the ecosystem.</p>



<a name="201861577"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201861577" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Henri Sivonen <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201861577">(Jun 24 2020 at 15:19)</a>:</h4>
<p>Before starting a group, I wanted a place for answering the questions that, from experience, I know will come up. To that end, I created a <a href="https://github.com/hsivonen/rfcs/blob/ppv/text/0000-ppv.md#faq">fork of the closed RFC with a FAQ section added</a>.</p>
<p>Due to the history of the <code>simd</code> crate and the <code>packed_simd</code> crate, I still wish to push for merging the existing crate instead of starting from starting discussion as if running code didn't already exist. <code>packed_simd</code> is already an attempt to start from scratch. We should value running code. With a task this large, otherwise, there's the risk of always getting almost there, the project getting abandoned and the next person redesigning the whole thing, getting almost there, and the cycle continuing. For this reason, I think it's important that effort is cumulative towards getting the running code into the standard library instead of starting from scratch again. (As a practical matter, I may have the bandwidth to advocate from <code>packed_simd</code>, but I for sure don't have the bandwidth to implement a different design.)</p>



<a name="201881217"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201881217" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201881217">(Jun 24 2020 at 17:52)</a>:</h4>
<p>I want to be clear about something here: it is <em>entirely possible</em> that the net result of the discussion will be to merge some form of <code>packed_simd</code> into <code>std</code>. The concern is that that cannot be the <em>starting point</em> of the discussion. We can't start the discussion of "how do we solve this problem" with "we're going to solve it <em>this specific way</em> or not at all".</p>



<a name="201881259"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201881259" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201881259">(Jun 24 2020 at 17:53)</a>:</h4>
<p>We cannot just have a pro-forma discussion of "how are we going to rubber-stamp this particular library without any actual discussion or changes".</p>



<a name="201881316"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201881316" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201881316">(Jun 24 2020 at 17:53)</a>:</h4>
<p>Also, nobody is saying "let's redesign from scratch".</p>



<a name="201881653"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201881653" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201881653">(Jun 24 2020 at 17:56)</a>:</h4>
<p>I don't think it's unreasonable to make sure we're in agreement on the requirements and that we will have a solution that meets them. I don't think it's reasonable to decide in advance that the requirements are "whatever this specific crate does because we're not changing it".</p>



<a name="201881733"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201881733" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201881733">(Jun 24 2020 at 17:57)</a>:</h4>
<p>I very much understand the scenario you're concerned about, and <em>I do not want to see that happen either</em>.</p>



<a name="201881772"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201881772" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201881772">(Jun 24 2020 at 17:57)</a>:</h4>
<p>I don't think anyone does. Wasted effort is a terrible thing.</p>



<a name="201881976"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201881976" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201881976">(Jun 24 2020 at 17:58)</a>:</h4>
<p>Also, portions of that FAQ are incredibly useful. There are a few answers in that FAQ that I would disagree with, but much of it I'm in complete agreement with.</p>



<a name="201882346"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201882346" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201882346">(Jun 24 2020 at 18:01)</a>:</h4>
<p>In any case, I really don't want to litigate specific points of that FAQ point-by-point right now. My concern is that we need to be <em>able</em> to have that discussion, without the answers being "no, because that's not what <code>packed_simd</code> currently does".</p>



<a name="201883190"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201883190" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201883190">(Jun 24 2020 at 18:09)</a>:</h4>
<p>To give just two specific examples:</p>
<ul>
<li>I'm not saying "let's redesign our entire strategy for handling <code>cpuid</code>". I'm saying "let's have a strategy for being <em>able</em> to do runtime detection and calling pre-compiled functions with different target features, without runtime overhead inside inner loops". That strategy might be as simple as some examples showing how to have two different functions compiled with different target features, inside which the portable SIMD methods will compile to different code (which may need some extra language support to make sure those methods get inlined two different ways), and then showing how to use a function pointer to decide which to call. I want to make sure something like that <em>works</em>, and that there isn't some fundamental blocker to doing so. That's an example of what I mean by talking through requirements.</li>
<li>You said that "When the target supports SIMD vectors of a given width, the portable SIMD types of that width is guaranteed to be zero-cost transmutable to the corresponding std::arch type.". Given that, could we add <em>safe</em> <code>From</code> impls that allow a zero-cost safe <code>.into()</code>? Is there something preventing us from doing that? If not, adding that would substantially improve the usability of a combination of portable SIMD and target-specific SIMD.</li>
</ul>



<a name="201883235"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201883235" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201883235">(Jun 24 2020 at 18:09)</a>:</h4>
<p>These are exactly the kinds of things a project group could talk through and find solutions to. And they would not <em>necessarily</em> result in a massive amount of additional work or rework or rewriting.</p>



<a name="201883849"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201883849" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201883849">(Jun 24 2020 at 18:15)</a>:</h4>
<p>FWIW, a few points of the FAQ I <em>enthusiastically</em> agree with, and very much want to see remain as requirements: yes, we should absolutely have shuffles even if not every platform uses them; yes, we should absolutely pick a layout that lets people rely on endianness; and I don't think we should wait on const generics either.</p>



<a name="201883992"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201883992" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201883992">(Jun 24 2020 at 18:16)</a>:</h4>
<p>(That last one is a major reason why I want to make sure we have a good solution for runtime detection, because I think it'll be critical for people to know if their platform has 128/256/512-bit vectors and write algorithms accordingly.)</p>



<a name="201884212"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201884212" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201884212">(Jun 24 2020 at 18:18)</a>:</h4>
<p>Also, regarding ABI, if the target supports SIMD vectors of a given width, and the portable SIMD types are guaranteed to be zero-cost transmutable, then making it possible to pass those in the ABI-defined vector registers seems valuable. That doesn't have to happen in the very first version, but having it as a requirement and putting it on the roadmap will help make sure we don't have a design decision that makes it impossible to do so.</p>



<a name="201958589"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201958589" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Henri Sivonen <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201958589">(Jun 25 2020 at 11:49)</a>:</h4>
<p>I filed <a href="https://github.com/rust-lang/compiler-team/issues/321">an MCP</a>, but I fail to find the Zulip stream that I'm supposed to post it to.</p>
<p>Regarding <code>cpuid</code>-based run-time multiversioning, I think portable SIMD should not be blocked by it. It has applicability beyond SIMD to e.g. <code>popcnt</code>, so I think it should be a separate project on its own.</p>
<p>I agree that adding <code>From</code> and <code>.into()</code> as appropriate makes sense. It's not essential for it to be part of the initial landing. It could be added later. Or at the initial landing. I'm not at all suggesting that nothing could be added to <code>packed_simd</code>. I'm interested in getting it landed after which for sure people will think of features to add.</p>



<a name="201960500"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201960500" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> bjorn3 <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201960500">(Jun 25 2020 at 12:12)</a>:</h4>
<p><span class="user-mention silent" data-user-id="314350">Henri Sivonen</span> <a href="#narrow/stream/196563-t-lang.2Fwg-meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd/near/201958589">said</a>:</p>
<blockquote>
<p>I filed <a href="https://github.com/rust-lang/compiler-team/issues/321">an MCP</a>, but I fail to find the Zulip stream that I'm supposed to post it to.</p>
</blockquote>
<p><a href="#narrow/stream/233931-xxx/topic/Portable.20SIMD.20project.20group.20compiler-team.23321">https://rust-lang.zulipchat.com/#narrow/stream/233931-xxx/topic/Portable.20SIMD.20project.20group.20compiler-team.23321</a></p>



<a name="201960816"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201960816" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> bjorn3 <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201960816">(Jun 25 2020 at 12:16)</a>:</h4>
<blockquote>
<p>NEON is opt-in in the third two-bit case</p>
</blockquote>
<p>*thirty-two-bit</p>



<a name="201960906"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201960906" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> bjorn3 <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201960906">(Jun 25 2020 at 12:17)</a>:</h4>
<blockquote>
<p>my bother<br>
*why</p>
</blockquote>



<a name="201987436"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/201987436" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Henri Sivonen <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#201987436">(Jun 25 2020 at 15:49)</a>:</h4>
<p>Thanks for the link to the right stream. I fixed the errors you found. Thanks.</p>



<a name="202025899"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/202025899" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#202025899">(Jun 25 2020 at 21:15)</a>:</h4>
<p>heh, that should probably have been a lang-team MCP</p>



<a name="202025936"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/202025936" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#202025936">(Jun 25 2020 at 21:15)</a>:</h4>
<p>sorry <span class="user-mention" data-user-id="314350">@Henri Sivonen</span> :) that is, on this repo <a href="https://github.com/rust-lang/lang-team/">https://github.com/rust-lang/lang-team/</a></p>



<a name="202026041"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/202026041" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#202026041">(Jun 25 2020 at 21:16)</a>:</h4>
<p>anyway, I think my take is that it is indeed a good idea to not start from a frame of "just adopt this thing" but I also wouldn't want to spend too much time relitigating everything, there is value in continuity</p>



<a name="202037815"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/202037815" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#202037815">(Jun 25 2020 at 23:32)</a>:</h4>
<p>That's a reasonable phrasing. I don't want to see anything relitigated, I just want to make sure there's alignment on the requirements and understanding of how to achieve those requirements with whatever plan we go with.</p>



<a name="202065517"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/202065517" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Henri Sivonen <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#202065517">(Jun 26 2020 at 08:44)</a>:</h4>
<p>OK. I filed a <a href="#narrow/stream/243200-xxx/topic/Portable.20SIMD.20project.20group.20lang-team.2329">lang team MCP</a>. Should I close the compiler one?</p>



<a name="202141089"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196563-t-lang/meta/topic/Promoting%20packed_simd%20to%20std%3A%3Asimd/near/202141089" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/196563-t-lang/meta/topic/Promoting.20packed_simd.20to.20std.3A.3Asimd.html#202141089">(Jun 26 2020 at 20:52)</a>:</h4>
<p><span class="user-mention" data-user-id="314350">@Henri Sivonen</span> yep</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>